[ALICE3] Explicitly set ccdb manager in geometryContainer instances#15196
Merged
njacazio merged 1 commit intoAliceO2Group:masterfrom Feb 28, 2026
Merged
[ALICE3] Explicitly set ccdb manager in geometryContainer instances#15196njacazio merged 1 commit intoAliceO2Group:masterfrom
njacazio merged 1 commit intoAliceO2Group:masterfrom
Conversation
github-actions
bot
changed the title
njacazio
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@njacazio about ~30% of the jobs on HY seem to crash and I managed to reproduce it locally. It seems like we tried to add a geometry entry before setting the ccdb manager. This PR should fix that (it works locally). But what has me really confused is why 70% of the jobs were ok in the first place
edit: Since the ccdb manager was already set in the init of the onTheFlyGeometryProvider I think that the crash happened in cases where the init of the other tasks were called before the onTheFlyGeometryProvider